|
•
|
Counter: A counter records incremental data cumulatively and rolls over when the counter limit is reached.
|
|
•
|
Gauge: A gauge statistic indicates a single value; a snapshot representation of a single point in time within a defined time frame. The gauge changes to a new value with each snapshot though a value may repeat from one period to the next. The limit depends upon the data type.
|
|
•
|
Information: This type of statistic provides information, often intended to differentiate sets of statistics; for example, a VPN name or IP address. The type of information provided depends upon the data type.
|
|
•
|
Int32/Int64: An integer, either 32-bit or 64-bit:
|
|
•
|
|
•
|
Float: A numeric value that can be represented fractionally; for example, 1.345.
|
|
•
|
String: A series of ASCII alphanumeric characters in a single grouping, usually pre-configured.
|
Important: Unless otherwise indicated, all statistics are counters and all statistics are standards-based.|
Description The name of the context configured on the system that is currently facilitating the GPRS service.
Type: Information
|
||
|
Description The identification number of the context configured on the system that is currently facilitating the GPRS service. This is an internal reference number.
Type: Information
|
||
|
Description The name of the GPRS service configured on the system for which the statistics are displayed.
Type: Information
|
||
|
Description The network service entity identifier in this GPRS service.
Type: Information
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) size messages received by the SGSN.
Triggers: Increments upon receiving the SNS size from the BSC.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of ACK messages sent for Sub-Network Service (SNS) messages by the network service entity.
Triggers: Increments after sending a SNS size ACK to the BSC.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS size messages failed due to unknown network service entity.
Triggers: Increments upon receiving SNS size messages from an unknown NSE (such as a BSC) with the reset flag unset.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages received by the SGSN.
Triggers: Increments upon receiving SNS configuration from the BSC.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages sent by the SGSN.
Triggers: Increments after sending SNS configuration to the BSC.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration ACK messages sent by the SGSN.
Triggers: Increments after sending SNS configuration ACK to the BSC.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration ACK messages received by the SGSN.
Triggers: Increments upon receiving SNS configuration ACK from the BSC.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed as received packet data unit was not compatible with the message state in the SGSN.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed as sent packet data unit was not compatible with the message state in the peer entity.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed due to invalid number of IPv4 endpoints in a received message.
Triggers: Increments when the number of IPv4 endpoints received in an SNS configuration message exceeds the maximum number of endpoints (received in SNS size messages).
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed due to invalid number of IPv4 endpoints in a sent message.
Triggers: Increments upon receiving SNS configuration ACK from a BSC with cause indicating an invalid number of IPv4 endpoints.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed due to invalid number of IPv6 endpoints in a received message.
Triggers: Increments when the number of IPv6 endpoints received in an SNS configuration message exceeds the maximum number of endpoints (received in SNS size messages).
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed due to invalid number of IPv6 endpoints in sent message.
Triggers: Increments upon receiving SNS configuration ACK from a BSC with cause indicating an invalid number of IPv6 endpoints.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed due to an unspecified protocol error in a received message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed due to unspecified protocol error in a sent message.
Triggers: Increments upon receiving SNS configuration ACK from a BSC with cause indicating an unspecified protocol error.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed due to invalid mandatory parameters in a received message.
Triggers: Increments upon receiving SNS configuration with an IP address of 0.0.0.0 or 255.255.255.255.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed due to invalid mandatory parameters in a sent message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed due to internal error in a received message.
Triggers: Increments upon receiving an unexpected SNS configuration or the peer NSVL configuration fails in the SGSN due to a software issue.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed due to internal error in a sent message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed due to invalid weight bit in a received message.
Triggers: Increments when the total signaling or data weight of all endpoints received in the SNS configuration is zero.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration messages failed due to invalid weight bit in a sent message.
Triggers: Increments upon receiving SNS configuration ACK from a BSC with cause indicating invalid weights.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of Sub-Network Service (SNS) configuration message failed due to no response from a peer.
Triggers: Increments following the expiration of a TSNS provisioning (all attempts over) for a SNS configuration.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages received.
Triggers: Increments upon receiving an SNS-ADD message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages sent.
Triggers: Increments after sending an SNS-ADD message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed as received packet data unit was not compatible with the message state in the SGSN.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed as sent packet data unit was not compatible with the message state in the peer entity.
Triggers: Increments upon receiving an SNS-ACK with a cause code indicating the PDU is not compatible with the protocol for the SNS-ADD message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed due to an invalid number of IPv4 endpoints in a received message.
Triggers: Increments when the number of IPv4 endpoints received in an SNS-ADD message plus the number of IPv4 endpoints received in the SNS configuration exceeds the maximum number of endpoints (as received in the SNS size message).
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed due to invalid number of IPv4 endpoints in a sent message.
Triggers: Increments on receiving SNS-ACK with cause “invalid number of IPv4 endpoints” for SNS-ADD.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed due to invalid number of IPv6 endpoints in a received message.
Triggers: Increments when the number of IPv6 endpoints received in an SNS-ADD message plus the number of IPv6 endpoints received in the SNS configuration exceeds the maximum number of endpoints (as received in the SNS size message).
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed due to invalid IPv6 address of endpoint in a sent message.
Triggers: Increments on receiving SNS-ACK with cause “invalid number of IPv6 endpoints” for SNS-ADD.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed due to an unspecified protocol error in a received message.
Triggers: Increments when an SNS-ADD is received before the SNS configuration.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed due to unspecified protocol error in sent message.
Triggers: Increments on receiving SNS-ACK with cause “protocol error-unspecified”.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed due to invalid mandatory parameters in received message.
Triggers: Increments upon receiving an SNS-ADD containing an IP address of 0.0.0.0 or 255.255.255.255.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed due to invalid mandatory parameters in sent message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed due to internal error in received message.
Triggers: Increments upon receiving an SNS-ADD if the SGSN is not able to create an NSVC towards the new remote endpoint due to an internal error.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed due to internal error in sent message.
Triggers: Increments after sending an SNS-ACK with a cause code indicating equipment failure for the SNS-ADD.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed due to invalid weight bit in received message.
Triggers: Increments upon receiving an SNS-ADD if the total sum of the signaling or data weight of all remote endpoint is 0 (zero).
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed due to invalid weight bit in sent message.
Triggers: Increments after sending an SNS-ACK with a cause code indicating invalid weights for the SNS-ADD.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ADD messages failed due to no response from peer.
Triggers: Increments following the expiration of a TSNS-PROV (all attempts over) for SNS-ADD.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages received.
Triggers: Increments upon receiving a SNS-DELETE message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages sent.
Triggers: Increments after sending a SNS-DELETE message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages failed as received packet data unit was not compatible with the message state in the SGSN.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages failed as sent packet data unit was not compatible with the message state in the remote entity.
Triggers: Increments upon receiving an SNS-ACK with a cause code indicating the PDU is not compatible with the protocol for the SNS-DELETE message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages failed due to an unknown IP endpoint in a received message.
Triggers: Increments when a SNS-DELETE is received from an unknown NSE or the SNS-DELETE contains all unknown IP endpoints.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages failed due to unknown endpoint in a sent message.
Triggers: Increments upon receiving an SNS-ACK with a cause code indicating the SNS-DELETE message contains unknown IP endpoints.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages failed due to invalid IP address in a received message.
Triggers: Increments when the SNS-DELETE contains an unknown IP address.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages failed due to invalid IP address in a sent message.
Triggers: Increments upon receiving an SNS-ACK with a cause code indicating the SNS-DELETE message contained an unknown IP address.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages failed due to unspecified protocol error in received message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages failed due to unspecified protocol error in sent message.
Triggers: Increments upon receiving an SNS-ACK with a cause code indicating the SNS-DELETE message contained an unspecified protocol error.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages failed due to invalid mandatory parameters in received message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages failed due to invalid mandatory parameters in sent message.
Triggers: Increments upon receiving an SNS-ACK with a cause code indicating the SNS-DELETE message contained an invalid essential information element (IE).
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages failed due to internal error in received message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages failed due to internal error in sent message.
Triggers: Increments after sending an SNS-ACK with a cause code indicating “internal error” for the SNS-DELETE.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-DELETE messages failed due to no response from peer.
Triggers: Increments following the expiration of TSNS provisioning (all attempts over) for SNS-DELETE.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight size messages received by the SGSN.
Triggers: Increments upon receiving a SNS-change-weight message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight messages sent by the SGSN.
Triggers: Increments after sending a SNS-change-weight message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight messages that failed as the received PDU was not compatible with the message state.
Triggers: Increments upon receiving an SNS-change-weight from an unknown NSE.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight messages sent by the SGSN that failed because the sent PDU was not compatible with the message state.
Triggers: Increments after sending an SNS-ACK with a cause code indicating the PDU is not compatible with the protocol for the SNS-change-weight message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight messages that failed due to invalid weight in the received message.
Triggers: Increments when applying the weights received in a SNS-change-weight message would result in the total weight equaling zero.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight messages sent by the SGSN that failed due to invalid weight in the sent message.
Triggers: Increments upon receiving an SNS-ACK with a cause code indicating the SNS-change-weight message contains invalid weights.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight messages that failed due to unknown IP endpoint in the received message.
Triggers: Increments when the SGSN receives an SNS-change-weight message containing an unknown IP endpoint.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight messages sent by the SGSN that failed due to unknown IP endpoint in the sent message.
Triggers: Increments upon receiving an SNS-ACK with a cause code indicating the SNS-change-weight message contained an unknown IP endpoint.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight messages that failed due to an unknown IP address in the received message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight messages sent by the SGSN that failed due to unknown IP address in sent message.
Triggers: Increments upon receiving an SNS-ACK with a cause code indicating the SNS-change-weight message contained an unknown IP address.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight message failed due to unspecified protocol error in received message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight message sent by the SGSN failed due to unspecified protocol error in sent message.
Triggers: Increments upon receiving an SNS-ACK with a cause code indicating the SNS-change-weight message contained an unspecified protocol error.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight message failed due to invalid mandatory parameters in received message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight messages sent by the SGSN which failed due to invalid mandatory parameters in the sent messages.
Triggers: Increments upon receiving an SNS-ACK with a cause code indicating the SNS-change-weight message contained an invalid essential information element (IE).
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight messages that failed due to internal error(s) in the received message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight messages sent by the SGSN that failed due to internal error(s) in the sent message.
Triggers: Increments after sending an SNS-ACK with a cause code indicating equipment failure for the SNS-change-weight.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-change-weight messages sent by the SGSN that failed due to no response from the peer.
Triggers: Increments following the expiration of a TSNS provisioning attempt for a SNS-change-weight.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ACK messages received.
Triggers: Increments upon receiving an SNS-ACK.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNS-ACK messages sent.
Triggers: Increments after sending an SNS-ACK.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of unknown messages received.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of NS-STATUS messages sent in response to SNS messages or because of NSVC going down.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC packets dropped at the BSSGP layer.
Triggers: Increments upon dropping of an LLC packet.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC packets dropped at the BSSGP layer because of unknown BVC.
Triggers: Increments upon dropping of an LLC packet due to unknown BVC.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC packets dropped at the BSSGP layer because of blocked BVC.
Triggers: Increments upon dropping of an LLC packet due to blocked BVC.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC packets dropped at the BSSGP layer because of encoding failure.
Triggers: Increments upon dropping of an LLC packet due to encoding failure.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of flow control BVC messages received from the BSC.
Triggers: Increments upon receipt of a flow control BVC message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of flow control BVC ACK messages sent to the BSC
Triggers: Increments after sending a flow control BVC ACK message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BVC-Block messages received from the BSC.
Triggers: Increments upon receiving a BVC-Block message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BVC BLOCK ACK messages sent.
Triggers: Increments after sending a BVC-Block-Ack message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BVC UNBLOCK messages received.
Triggers: Increments upon receiving a BVC-Unblock message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BVC UNBLOCK ACK messages sent.
Triggers: Increments after sending a BVC-Unblock-Ack message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BVC RESET messages sent.
Triggers: Increments after sending a BVC-Reset message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BVC RESET messages received.
Triggers: Increments upon receiving a BVC-Reset message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BVC RESET ACK messages sent.
Triggers: Increments after sending a BVC-Reset-Ack message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BVC RESET ACK messages received.
Triggers: Increments upon receiving a BVC-Reset-Ack message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BVC status messages sent.
Triggers: Increments after sending a BVC-Status message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BVC status messages received.
Triggers: Increments upon receiving a BVC-Status message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP FLUSH LL (Logical Link) messages sent.
Triggers: Increments after sending a Flush-LL message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP FLUSH LL (Logical Link) ACK messages received.
Triggers: Increments upon receiving a Flush-LL-Ack message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP circuit switched (CS) paging messages sent.
Triggers: Increments after sending a CS-Paging message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP packet switched (PS) paging messages sent.
Triggers: Increments after sending a PS-Paging message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP routing area (RA) capability update messages received.
Triggers: Increments upon receiving a RA-Capability-Update message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP routing area (RA) capability update messages sent.
Triggers: Increments after sending a RA-Capability-Update-Ack message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP radio status messages received.
Triggers: Increments upon receiving a Radio-Status message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP SUSPEND messages received.
Triggers: Increments upon receiving a BSSGP-Suspend message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP SUSPEND Acks sent.
Triggers: Increments after sending a BSSGP-Suspend-Ack message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP SUSPEND NAcks sent.
Triggers: Increments after sending a BSSGP-Suspend-Nak message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP RESUME messages received.
Triggers: Increments upon receiving a BSSGP-Resume message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP RESUME Acks sent.
Triggers: Increments after sending a BSSGP-Resume-Ack message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP RESUME NAcks sent.
Triggers: Increments after sending a BSSGP-Resume-Nak message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP unit data sent in downlink direction (towards MS).
Triggers: Increments after sending a BSSGP DL-UNITDATA message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP unit data received in uplink direction (towards network).
Triggers: Increments upon receiving a BSSGP UL-UNITDATA message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC PDU discard messages received.
Triggers: Increments upon receiving a LLC-Discard message.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP packets dropped because the flow control buffer was full.
Triggers: Increments after dropping a downlink packet in the BSSGP layer due to a full flow control queue.
Availability: per SGSN
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP packets dropped in downlink direction.
Triggers: Increments after dropping a downlink packet in the BSSGP layer.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of MS flow control messages received.
Triggers: Increments upon receiving a MS-Flow-Control message.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of MS flow control ACK messages sent.
Triggers: Increments after sending a MS-Flow-Control-Ack message.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP-STATUS messages received.
Triggers: Increments upon receiving a BSSGP-STATUS message as a response for any BSSGP message which contains an MS identity that is not known at the BSS.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of BSSGP-STATUS messages sent.
Triggers: Increments after sending a BSSGP-STATUS message as a response for the received BSSGP message if the MS identity is not known by the SGSN.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of MS initiated eXchange Identification (XID) indicators received.
Triggers: Increments upon receiving a XID request from a MS with Layer 3/SNDCP XID parameters.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SGSN initiated eXchange Identification (XID) indicators sent.
Triggers: Increments after sending a XID request from the SGSN with Layer 3/SNDCP XID parameters.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNDCP network PDUs in LLC Acknowledged mode received from MS.
Triggers: Increments upon receiving SNDCP network PDUs in LLC Acknowledged mode from the MS.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNDCP network PDUs in LLC Acknowledged mode sent to MS.
Triggers: Increments after sending SNDCP network PDUs in LLC Acknowledged mode to the MS.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNDCP network PDUs in UnLLC Acknowledged mode received from MS.
Triggers: Increments upon receiving SNDCP network PDUs in Un-LLC Acknowledged mode from the MS.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNDCP network PDUs in UnLLC Acknowledged mode sent to MS.
Triggers: Increments after sending SNDCP network PDUs in un-LLC Acknowledged mode to the MS.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNDCP bytes received from MS for all subscribers at SNDCP layer using LLC Acknowledged mode of LLC operation.
Triggers: Increments after the uplink data packet has passed SNDCP validations as mentioned in sections 6.7 and 6.9 of SNDCP TS 44.065.
Availability: per GPRS service, per Routing Area
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNDCP bytes sent to MS for all subscribers at SNDCP layer using LLC Acknowledged mode of LLC operation.
Triggers: Increments after the uplink data packet has passed SNDCP validations as mentioned in sections 6.7 and 6.9 of SNDCP TS 44.065.
Availability: per GPRS service, per Routing Area
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNDCP bytes received from MS for all subscribers at SNDCP layer using LLC Un-acknowledged mode of LLC operation.
Triggers: Increments after the uplink data packet has passed SNDCP validations as mentioned in sections 6.7 and 6.9 of SNDCP TS 44.065.
Availability: per GPRS service, per Routing Area
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNDCP bytes sent to MS for all subscribers at SNDCP layer using LLC Un-acknowledged mode of LLC operation.
Triggers: Increments after the uplink data packet has passed SNDCP validations as mentioned in sections 6.7 and 6.9 of SNDCP TS 44.065.
Availability: per GPRS service, per Routing Area
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNDCP PDUs dropped when received from LLC due to invalid parameter or state.
Triggers: Increments upon receiving a SNDCP PDU from LLC for a SAPI which is not in a bound state.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNDCP PDUs dropped due to invalid reference number received from LLC.
Triggers: Increments upon receiving an invalid reference number from LLC for the SAPI in which the SNDCP PDU is received.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNDCP network PDUs sent/transferred to other SGSNs during inter-SGSN routing area update (RAU).
Triggers: Increments after sending SNDCP network PDUs to a peer SGSN while Inter-SGSN RAU is in progress.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of SNDCP network PDUs received from other SGSNs during inter-SGSN routing area update (RAU).
Triggers: Increments upon receiving SNDCP network PDUs from a peer SGSN while Inter-SGSN RAU is in progress.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC data requests received from the MS.
Triggers: Increments upon receiving a downlink packet from SNDCP.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC data requests confirmation sent to the MS.
Triggers: Increments after sending a confirmation to SNDCP regarding a downlink packet.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC data indications sent to SNDCP layer.
Triggers: Increments after sending an uplink packet to SNDCP.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC unit data requests received from the MS.
Triggers: Increments upon receiving an Un-LLC Acknowledged mode packet from SNDCP.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC unit data indications sent to the MS.
Triggers: Increments after sending an Un-LLC Acknowledged mode packet to SNDCP.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of frames received from the MS that are discarded at the LLC layer.
Triggers: Increments after discarding a packet received from BSSGP.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC error frames received from the MS.
Triggers: Increments upon receiving a packet with an error from BSSGP.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC unrecognized frames received from the MS.
Triggers: Increments upon receiving a LLC message which contains an Invalid Frame format or a format other than the defined frame formats.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC exchange identifier (XID) request collisions.
Triggers: Increments upon receiving a XID while waiting for DISC/SABME.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC ciphering errors.
Triggers: Increments upon a deciphering failure on the received LLC frame or on a ciphering failure while building the LLC frame.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC frame check sequence errors.
Triggers: Increments upon a Frame Check Sequence failure while validating FCS on the received LLC frame or on a FCS failure while building the LLC frame.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of bytes of LLC frames received from an MS. This value includes all LLC messages (data + gmm messages + other LLC messages).
Triggers: Increments when the LLC layer receives a packet (can be UI frame, U frame, S frame or U frame) from lower BSSGP layer.
Availability: per GRPS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of bytes sent from the LLC layer to an MS from the SGSN. This value includes all LLC messages (data + gmm messages + other LLC messages).
Triggers: Increments when the LLC layer sends a packet (can be UI frame, U frame, S frame or U frame) to the lower BSSGP layer.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of unacknowledged UI frames received at the LLC layer from an MS.
Triggers: Increments when the LLC layer receives a UI frame in unacknowledged mode from the lower BSSGP layer.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of unacknowledged UI frames sent from the LLC to an MS.
Triggers: Increments when the LLC layer sends a UI frame in unacknowledged mode to the lower BSSGP layer.
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC frames with unnumbered information received from the MS.
Triggers: Increments upon receiving a LLC message from the MS which contains an Unnumbered Information (UI Frame).
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC frames with unnumbered information sent to the MS. This is a counter type of statistic.
Triggers: Increments after sending a LLC message to the MS which contains an Unnumbered Information (UI Frame).
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC frames with ciphered unnumbered information received from the MS. This is a counter type of statistic.
Triggers: Increments upon receiving a LLC message from the MS which contains a Ciphered Unnumbered Information (UI Frame).
Availability: per GPRS service
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of LLC frames with ciphered unnumbered information sent to the MS.
Triggers: Increments after sending a LLC message to the MS which contains a Ciphered Unnumbered Information (UI Frame).
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Indicates the total number of GEA1 ciphered data frames received at LLC layer; where the data frames include GMM, SMS, and SNDCP SAPI i.e 1, 7, 3,5,9 or 11.
Triggers: Increments when receiving data frame ciphered with the GPRS GEA1 ciphering algorithm.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Indicates the total number of GEA1 ciphered data frames transmitted from the LLC layer; where the data frames include GMM, SMS, and SNDCP SAPI i.e., 1, 7, 3, 5, 9 or 11.
Triggers: Increments when transmitting data frame ciphered with the GPRS GEA1 ciphering algorithm.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Indicates the total number of GEA1 ciphered data bytes received at the LLC layer.
Triggers: Increments when receiving a data octet ciphered with GPRS GEA1 ciphering algorithm.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Indicates the total number of GEA1 ciphered data bytes transmitted from the LLC layer.
Triggers: Increments when transmitting a data octet ciphered with GPRS GEA1 ciphering algorithm.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Indicates the total number of GEA2 ciphered data frames received at LLC layer; where the data frames include GMM, SMS, and SNDCP SAPI i.e., 1, 7, 3, 5, 9 or 11.
Triggers: Increments when receiving data frame ciphered with the GPRS GEA2 ciphering algorithm.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Indicates the total number of GEA2 ciphered data frames transmitted from the LLC layer; where the data frames include GMM, SMS, and SNDCP SAPI i.e., 1, 7, 3, 5, 9 or 11.
Triggers: Increments when transmitting data frame ciphered with the GPRS GEA2 ciphering algorithm.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Indicates the total number of GEA2 ciphered data bytes received at the LLC layer.
Triggers: Increments when receiving a data octet ciphered with GPRS GEA2 ciphering algorithm.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Indicates the total number of GEA2 ciphered data bytes transmitted from the LLC layer.
Triggers: Increments when transmitting a data octet ciphered with GPRS GEA2 ciphering algorithm.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Indicates the total number of GEA3 ciphered data frames received at LLC layer; where the data frames include GMM, SMS, and SNDCP SAPI i.e., 1, 7, 3, 5, 9 or 11.
Triggers: Increments when receiving data frame ciphered with the GPRS GEA3 ciphering algorithm.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Indicates the total number of GEA3 ciphered data frames transmitted from the LLC layer; where the data frames include GMM, SMS, and SNDCP SAPI i.e., 1, 7, 3, 5, 9 or 11.
Triggers: Increments when transmitting data frame ciphered with the GPRS GEA3 ciphering algorithm.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Indicates the total number of GEA3 ciphered data bytes received at the LLC layer, where the data frames include GMM, SMS, and SNDCP SAPI i.e., 1, 7, 3, 5, 9 or 11.
Triggers: Increments when receiving a data octet ciphered with GPRS GEA3 ciphering algorithm.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Indicates the total number of GEA3 ciphered data bytes transmitted from the LLC layer, where the data frames include GMM, SMS, and SNDCP SAPI i.e., 1, 7, 3, 5, 9 or 11.
Triggers: Increments when transmitting a data octet ciphered with GPRS GEA3 ciphering algorithm.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Total number of unciphered frames received at the LLC layer.
Triggers: Increments when the incoming frame is unciphered.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Total number of unciphered frames transmitted from the LLC layer.
Triggers: Increments when the outgoing frame is unciphered.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Total number of unciphered data frames received at the LLC layer, where the data frames include GMM, SMS, and SNDCP SAPI i.e., 1, 7, 3, 5, 9 or 11.
Triggers: Increments when the incoming data frame is unciphered.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Total number of unciphered data frames transmitted at the LLC layer, where the data frames include GMM, SMS, and SNDCP SAPI i.e., 1, 7, 3, 5, 9 or 11.
Triggers: Increments when the outgoing data frame is unciphered.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Total number of unciphered data bytes received at the LLC layer.
Triggers: Increments when receiving an unciphered data octet.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Total number of unciphered data bytes transmitted from the LLC layer.
Triggers: Increments when transmitting an unciphered data octet.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of XID-reset messages received from the MS.
Triggers: Increments when the LLC layer receives an XID request from the lower BSSGP layer.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of XID-reset messages sent to the MS. This includes responses to XIDs sent by the SGSN and XID command from the MS.
Triggers: Increments when the LLC layer sends an XID request to the lower BSSGP layer.
Availability: per GPRS service.
Type: Counter
|
||
|
Description: Stat collected on the Gb interface provides the total number of bytes of data sent by a SGSN to a specific BSC (NSEI).
Triggers: Increments by the number of bytes of data in the data packet whenever a data packet is sent in the downlink direction from the SGSN to a subscriber served by the particular BSC (NSEI).
Availability: per NSEI
Type: Counter
|
||
|
Description: Stat collected on the Gb interface provides the total number of data packets a SGSN sent to a specific BSC (NSEI).
Triggers: Increments whenever a data packet is sent in the downlink direction from the GGSN to a subscriber served by the particular BSC.
Availability: per NSEI
Type: Counter
|
||
|
Description: Stat collected on the Gb interface provides the total number of bytes of data received by a SGSN from a specific BSC (NSEI).
Triggers: Increments by the number of bytes of data in the data packet whenever a data packet is sent in the uplink direction to the SGSN from a subscriber served by the particular BSC (NSEI).
Availability: per BSC
Type: Counter
|
||
|
Description: Stat collected on the Gb interface provides the total number of data packets the SGSN received from a specific BSC (NSEI).
Triggers: Increments whenever a data packet is sent in the uplink direction to the SGSN from a subscriber served by the particular BSC (NSEI).
Availability: per NSEI
Type: Counter
|
||
|
Description: This proprietary statistic indicates the total number of currently attached GPRS subscribers whose MS network capability supports GEA0 (no ciphering).
Availability: per SGSN
Type: Gauge
|
||
|
Description: This proprietary statistic indicates the total number of currently attached GPRS subscribers whose MS network capability supports GEA1 encryption.
Availability: per SGSN
Type: Gauge
|
||
|
Description: This proprietary statistic indicates the total number of currently attached GPRS subscribers whose MS network capability supports GEA2 encryption.
Availability: per SGSN
Type: Gauge
|
||
|
Description: This proprietary statistic indicates the total number of currently attached GPRS subscribers whose MS network capability supports GEA3 encryption.
Availability: per SGSN
Type: Gauge
|
||
|
Description: This proprietary statistic indicates the total number of currently attached GPRS subscribers who have negotiated, with the SGSN during authentication and ciphering request, to use GEA0 (no ciphering).
Availability: per SGSN
Type: Gauge
|
||
|
Description: This proprietary statistic indicates the total number of currently attached GPRS subscribers who have negotiated, with the SGSN during authentication and ciphering request, to use GEA1 encryption.
Availability: per SGSN
Type: Gauge
|
||
|
Description: This proprietary statistic indicates the total number of currently attached GPRS subscribers who have negotiated, with the SGSN during authentication and ciphering request, to use GEA2 encryption.
Availability: per SGSN
Type: Gauge
|
||
|
Description: This proprietary statistic indicates the total number of currently attached GPRS subscribers who have negotiated, with the SGSN during authentication and ciphering request, to use GEA3 encryption.
Availability: per SGSN
Type: Gauge
|
||
 Important: See Bulk Statistics Overview for statistics that are common to all schema. |
||
